Personal digital key initialization and registration for secure transactions

ABSTRACT

A system and method provide efficient, secure, and highly reliable authentication for transaction processing and/or access control applications. A personal digital key (PDK) is programmed using a trusted programming device to initialize and/or register the PDK for use. In one embodiment, the initialization and registration processes are administered by a specialized trusted Notary to ensure the processes follow defined security procedures. In a biometric initialization, the programming device acquires a biometric input from a user and writes the biometric data to a tamperproof memory in the PDK. In registration, the Programmer communicates to one or more remote registries to create or update entries associated with the user PDK. Once initialized and registered, the PDK can be used for various levels of secure authentication processes.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S.application Ser. No. 14/448,891, entitled, “Personal Digital KeyInitialization and Registration for Secure Transactions,” filed on Jul.31, 2014, which is a continuation of U.S. application Ser. No.13/791,553, entitled, “Personal Digital Key Initialization andRegistration for Secure Transactions,” filed on Mar. 8, 2013, which is acontinuation of U.S. application Ser. No. 11/744,832, entitled “PersonalDigital Key Initialization and Registration for Secure Transactions”filed, May 5, 2007, which claims the benefit of U.S. ProvisionalApplication No. 60/798,172 entitled “Touch Pay” filed on May 5, 2006;U.S. Provisional Application No. 60/798,843 entitled “Touch Pay” filedon May 8, 2006; U.S. Provisional Application No. 60/838,788 entitled“Personal Digital Key Accessible Storage Device and Processor” filed onAug. 17, 2006; U.S. Provisional Application No. 60/824,758 entitled“Truprox Touch Technology” filed on Sep. 6, 2006; and U.S. ProvisionalApplication No. 60/894,608 entitled “TruProx Stored-Photo Extension”filed on Mar. 13, 2007, the entire contents of which are all hereinincorporated by reference.

Applicants hereby notify the USPTO that the claims of the presentapplication are different from those of the aforementioned relatedapplications. Therefore, Applicant rescinds any disclaimer of claimscope made in the parent application or any other predecessorapplication in relation to the present application. The Examiner istherefore advised that any such disclaimer and the cited reference thatit was made to avoid may need to be revisited at this time. Furthermore,the Examiner is also reminded that any disclaimer made in the presentapplication should not be read into or against the parent application,the grandparent application or any other related application.

BACKGROUND 1. Field of Art

The invention generally relates to electronic authentication, and morespecifically, to secure authentication using biometric verification. Inparticular, the present invention relates to the initialization andregistration of personal digital keys.

2. Description of the Related Art

Optimizing sales transactions and providing secure access to physicaland/or digital assets are challenges faced by many businesses andorganizations. Ensuring these processes are safe, efficient and simpleis important to merchants, providers, users and consumers alike.Conventionally, technologies such as magnetic cards (e.g., credit cards,debit cards, ATM cards, and employee badges) have been used in attemptto address these needs. More recently, various contactless cards ortokens requiring placement near compatible readers have been used.

Each of these technologies, however, has inherent problems in providingsecure transaction processing and access control. In particular, theconventional technologies fail to sufficiently ensure that individualsattempting to perform a transaction are associated with the accessdevice and are authorized to do so. Conventional attempts to addressthis issue include requiring users to provide Personal IdentificationNumbers (PINs) or passwords in conjunction with account numbers. Whilein some instances, these options have helped to combat fraudulentactivity, these solutions add unwanted complexity and delay totransactions. With the growing need to memorize various PINs andpasswords, individuals tend to repeatedly use the same, simple phrase toprotect many items, or worse, keep the written phrases in theirpurse/wallet or next to their computer. Thus, the use of PINs andpasswords are often defeated.

A technology better suited to address the issue of authenticating usersis biometrics. In biometric authentication, physical and/or behavioralcharacteristics of an individual are analyzed to uniquely identify theindividual. For example, biometric characteristics can includefingerprint, retinal, iris, face, palm, DNA, voice or signaturecharacteristics that can each be uniquely associated with theindividual. However, traditional biometric authentication solutions alsosuffer from significant problems. First, traditional biometricauthentication techniques typically expose the participating parties toserious liabilities, risks and inefficiencies. Conventional biometricauthentication techniques nearly always require users to releasepersonal, private and unchangeable data to a controlling-entity (e.g., amerchant or business authority) or to a third-party relied upon by thecontrolling-entity. This exposes an individual's personal biometricinformation to the possibility of theft and fraudulent use. Further,controlling entities must either assume the risks and liabilities ofstoring this data, or trust the data to a third-party's care.

Second, conventional biometric authentication techniques generallyrequire an individual to submit biometric information (e.g., afingerprint, retinal scan, facial scan, or signature) for storage in adatabase that can then be later used for comparison with biometric dataacquired at the point of transaction. This “enrollment” process istime-consuming, risky, error-prone and considered intrusive by manyindividuals. Further, the enrollment process must be repeated for eachindividual for every intended use. For example, a user may need toenroll for biometric authentication with his/her company (e.g., forsecure access to facilities or digital files), and separately enrollwith various merchants using biometric authentication for transactions.Thus, the individual has to spend significant time completing eachseparate enrollment, and additionally must trust each entity withhis/her personal biometric information. For these reasons alone manyindividuals do not even consider these options.

The above-defined issues represent serious roadblocks to the widespreaddeployment and acceptance of conventional biometric authenticationoptions. Unless the identified deficiencies are addressed, the fullpotential of biometric solutions will never be realized. Therefore, anew technology is needed that provides highly reliable, safe andefficient secure authentication for transaction-processing and/or accesscontrol. Moreover, the new technology should allow for a simple andefficient enrollment process that does not put an individual's highlypersonal information at risk of identity theft or other fraudulent use.

SUMMARY

A system and method provide efficient, secure and highly reliableauthentication for transaction processing and/or access controlapplications. A portable physical device, referred to herein as aPersonal Digital Key or “PDK”, stores one or more profiles (e.g., abiometric profile) in a tamper-proof memory. The biometric profile isacquired in a secure trusted process and is uniquely associated with anindividual that is authorized to use and is associated with the PDK. ThePDK can wirelessly transmit the identification information including aunique PDK identification number and the biometric profile over a securewireless channel for use in an authentication process. Additionally, thePDK can store other information such as credit/debit card information,bank information, or personal information in a memory for use inauthorizing or completing a transaction.

Typically, a receiving device, referred to herein as a Reader,wirelessly receives the profile from the PDK in order to process atransaction or provide access to secure digital or physical assets. Inone embodiment, the Reader acquires a biometric input from theindividual carrying the PDK at the point of transaction. The biometricinput can be acquired by, for example, a fingerprint scan, iris scan,retinal scan, palm scan, face scan, DNA analysis, signature analysis,voice analysis or any other input mechanism that provides physical orbehavioral characteristics uniquely associated with the individual. TheReader compares the biometric profile received from the PDK to thebiometric input obtained at the point of transaction to determine if atransaction should be authorized.

In one embodiment, the Reader is further adapted to communicate with oneor more remote registries to provide an additional layer of security inthe authentication process. Information transmitted from the PDK can becompared to entries stored in the registries to ensure the PDK (and itsowner) have not participated in any fraudulent use and that the PDK isnot invalid, lost or stolen. In yet another embodiment, one or morebiometric authentications, remote registry authentications or othertypes of authentication are used in combination.

The PDK is programmed by a programming device referred to herein as a“Programmer” during initialization and registration processes. In oneembodiment, the programming process is witnessed and authenticated by aspecialized trusted Notary. In one embodiment of the initializationprocess, the Programmer is communicatively coupled with a PDK from theuser and a PDK from the Notary. Information is read from the user PDK todetermine if the PDK is authorized for initialization and Notaryinformation is read from the Notary PDK to determine if the Notary isauthorized to perform the initialization. If both the user and theNotary are authorized, the Programmer prompts the user to provide abiometric input. The Notary witnesses the biometric acquisition processeither in person or remotely to ensure the information can be trusted.The Programmer then writes biometric profile data to a memory in theuser PDK. In one embodiment, the Programmer does not store the personalbiometric data.

In registration, the Programmer communicates to the Central Registryand/or one or more private entries to create or update entriesassociated with the user PDK. Registration allows the PDK owner to beauthenticated for transactions requiring registry authentication. Aregistry entry may include, for example, a unique PDK ID, purchasinginformation associated with the user and personal information associatedwith the user.

The initialization and registration processes further enhance securityby storing initialization/registration history data to both the user PDKand the Programmer memory. This data includes, for example, the user PDKID, the Notary PDK ID, the programmer ID, a site ID, or otherinformation associated with programming including software revisions,checksums and other metrics intended to verify the current softwareversions used in both the Programmer and the PDK. The history can berecalled in the future for auditing purposes.

The features and advantages described in the specification are not allinclusive and, in particular, many additional features and advantageswill be apparent to one of ordinary skill in the art in view of thedrawings, specification, and claims. Moreover, it should be noted thatthe language used in the specification has been principally selected forreadability and instructional purposes, and may not have been selectedto delineate or circumscribe the inventive subject matter.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a high level block diagram illustrating a system for secureelectronic authentication.

FIG. 2 is a block diagram illustrating one embodiment of a PersonalDigital Key (PDK).

FIG. 3 is a block diagram illustrating one embodiment of a Reader.

FIG. 4 is a flowchart illustrating one embodiment of a process forauthorizing a transaction using secure authentication.

FIG. 5 is a flowchart illustrating one embodiment of a process fordevice authentication by a Reader.

FIG. 6 is a flowchart illustrating one embodiment of a process forprofile authentication by a Reader.

FIG. 7A is a flowchart illustrating one embodiment of a process forprofile testing using a biometric input.

FIG. 7B is a flowchart illustrating one embodiment of a process forprofile testing using a personal identification number.

FIG. 7C is a flowchart illustrating one embodiment of a process forprofile testing using a picture profile.

FIG. 7D is a flowchart illustrating one embodiment of a process forprofile testing using a private or central registry.

FIG. 8 is a high level block diagram illustrating a system forinitializing and registering a PDK for use in secure electronicauthentication.

FIG. 9 is a block diagram illustrating one embodiment of a Programmerfor programming a PDK.

FIG. 10 is a flowchart illustrating one embodiment of a process for PDKinitialization.

FIG. 11 is a flowchart illustrating one embodiment of a process forvalidating a PDK for initialization.

FIG. 12 is a flowchart illustrating one embodiment of a process foracquiring biometric information for PDK initialization.

FIG. 13 is a flowchart illustrating one embodiment of a process forwriting initialization data.

FIG. 14 is a flowchart illustrating one embodiment of a process forregistering a PDK with a registry.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION

FIG. 1 is a high level block diagram illustrating a system for securelyauthenticating an individual for transaction-processing and/or accesscontrol applications. The system 100 comprises a Personal Digital Key(PDK) 102, a Reader 108, a network 110 and one or more externaldatabases including a validation database 112, a Central Registry 114and one or more private registries 116. The Reader 108 is coupled to thePDK 102 by a wireless link 106 and coupled to a network 110 by either awired or wireless link. The Reader 108 is also adapted to receive abiometric input 104 from a user and is capable of displaying status to auser. The network 110 couples the validation database 112, the CentralRegistry 114 and two private registries 116 to the Reader 108. Inalternative embodiments, different or additional external registries ordatabases may be coupled to the network 110. In another embodiment, theReader 108 operates as a standalone device without a connection to thenetwork 110.

The system 100 addresses applications where it is important to ensure aspecific individual is authorized to perform a given transaction. Atransaction as used herein can include executing a purchase or financialdealing, enabling access to physical and/or digital items, verifyingidentification or personal information or executing other tasks where itis important to authenticate an individual for use. Generally, theReader 108 wirelessly receives information stored in the PDK 102 thatuniquely identifies the PDK 102 and the individual carrying the PDK 102.The Reader 108 can also receive a biometric input 104 from theindividual. Based on the received information, the Reader 108 determinesif the transaction should be authorized. Beneficially, the system 100provides comprehensive authentication without the need for PINs orpasswords. Moreover, personal biometric information need not be storedin any local or remote storage database and is only stored on the user'sown PDK. Furthermore, in one embodiment, purchase transactions can beefficiently completed without requiring the use of physical creditcards, tokens or other user action beyond initiating the transaction.

The credibility of the system 100 is ensured by the use of a PDK 102that stores trusted information. The PDK 102 is a compact, portableuniquely identifiable wireless device typically carried by anindividual. The PDK 102 stores digital information in a tamper-proofformat that uniquely associates the PDK 102 with an individual. Exampleembodiments of PDKs are described in more detail in U.S. patentapplication Ser. No. 11/292,330, entitled “Personal Digital Key AndReceiver/Decoder Circuit System And Method” filed on Nov. 30, 2005; U.S.patent application Ser. No. 11/620,581 entitled “Wireless NetworkSynchronization Of Cells And Client Devices On A Network” filed on Jan.5, 2007; and U.S. patent application Ser. No. 11/620,577 entitled“Dynamic Real-Time Tiered Client Access” filed on Jan. 5, 2007, theentire contents of which are all incorporated herein by reference.

To establish the trust, credibility and confidence of the authenticationsystem, information stored in the PDK 102 is acquired by a process thatis trusted, audited and easily verified. The process is ensured by atrusted third-party system, referred to herein as a Notary, thatadministers the acquisition and storage of information in the PDK 102according to defined security protocols. In one embodiment, the Notaryis a system and/or a trusted individual that witnesses the acquisitionand storage either in person or remotely. In another embodiment, theNotary comprises trusted hardware that administers the initializationprocess by an automated system. Thus, once initialized by the trustedprocess, the PDK 102 can prove that the information it stores is that ofthe individual. Example embodiments of the initialization process aredescribed in more detail below with reference to FIGS. 8-14.

The Reader 108 wirelessly communicates with the PDK 102 when the PDK 102is within a proximity zone of the Reader 108. The proximity zone can be,for example, several meters in radius and can be adjusted dynamically bythe Reader 108. Thus, in contrast to many conventional RF ID devices,the Reader 108 can detect and communicate with the PDK 102 withoutrequiring the owner to remove the PDK 102 from his/her pocket, wallet,purse, etc. Generally, the Reader 108 receives uniquely identifyinginformation from the PDK 102 and initiates an authentication process forthe individual carrying the PDK 102. In one embodiment, the Reader 108is adapted to receive a biometric input 104 from the individual. Thebiometric input 104 comprises a representation of physical or behavioralcharacteristics unique to the individual. For example, the biometricinput 104 can include a fingerprint, a palm print, a retinal scan, aniris scan, a photograph, a signature, a voice sample or any otherbiometric information such as DNA, RNA or their derivatives that canuniquely identify the individual. The Reader 108 compares the biometricinput 104 to information received from the PDK 102 to determine if atransaction should be authorized. Alternatively, the biometric input 104can be obtained by a biometric reader on the PDK 102 and transmitted tothe Reader 108 for authentication. In additional alternative embodiment,some or all of the authentication process can be performed by the PDK102 instead of the Reader 108.

The Reader 108 is further communicatively coupled to the network 110 inorder to receive and/or transmit information to remote databases forremote authentication. In an alternative embodiment, the Reader 108includes a non-volatile data storage that can be synchronized with oneor more remote databases 112 or registries 114-116. Such an embodimentalleviates the need for a continuous connection to the network 110 andallows the Reader 108 to operate in a standalone mode and for the localdata storage to be updated when a connection is available. For example,a standalone Reader 108 can periodically download updated registryentries and perform authentication locally without any remote lookup.

The network 110 provides communication between the Reader 108 and thevalidation database 112, Central Registry 114 and one or more privateregistries 116. In alternative embodiments, one or more of theseconnections may not be present or different or additional networkconnections may be present. In one embodiment, the network 110 usesstandard communications technologies and/or protocols. Thus, the network110 can include links using technologies such as Ethernet, 802.11,802.16, integrated services digital network (ISDN), digital subscriberline (DSL), asynchronous transfer mode (ATM), etc. Similarly, thenetworking protocols used on the network 110 can include thetransmission control protocol/Internet protocol (TCP/IP), the hypertexttransport protocol (HTTP), the simple mail transfer protocol (SMTP), thefile transfer protocol (FTP), etc. The data exchanged over the network110 can be represented using technologies and/or formats including thehypertext markup language (HTML), the extensible markup language (XML),etc. In addition, all or some of links can be encrypted usingconventional encryption technologies such as the secure sockets layer(SSL), Secure HTTP and/or virtual private networks (VPNs). In anotherembodiment, the entities can use custom and/or dedicated datacommunications technologies instead of, or in addition to, the onesdescribed above.

The validation database 112 stores additional information that may beused for authorizing a transaction to be processed at the Reader 108.For example, in purchase transactions, the validation database 112 is acredit card validation database that is separate from the merchantproviding the sale. Alternatively, a different database may be used tovalidate different types of purchasing means such as a debit card, ATMcard, or bank account number.

The registries 114-116 are securely-accessible databases coupled to thenetwork 110 that store, among other items, PDK, Notary, and Readerinformation. In one embodiment, the registries 114-116 do not storebiometric information. In an alternative embodiment, a registry storesbiometric information in an encoded format that can only be recoveredusing an algorithm or encoding key stored in the PDK 102. Informationstored in the registries can be accessed by the Reader 108 via thenetwork 110 for use in the authentication process. There are two basictypes of registries illustrated: private registries 116 and the CentralRegistry 114. Private registries 116 are generally established andadministered by their controlling entities (e.g., a merchant, businessauthority, or other entity administering authentication). Privateregistries 116 can be custom configured to meet the specialized andindependent needs of each controlling entity. The Central Registry 114is a single highly-secured, centrally-located database administered by atrusted third-party organization. In one embodiment, all PDKs 102 areregistered with the Central Registry 114 and may be optionallyregistered with one or more selected private registries 116. Inalternative embodiments, a different number or different types ofregistries may be coupled to the network 110.

Turning now to FIG. 2, an example embodiment of a PDK 102 isillustrated. The PDK 102 comprises a memory 210, a programmer I/O 240,control logic 250, and a transceiver 260, coupled by a bus 270. The PDK102 can be standalone as a portable, physical device or can beintegrated into commonly carried items. For example, a PDK 102 can beintegrated into a portable electronic device such as a cell phone,Personal Digital Assistant (PDA), or GPS unit, an employeeidentification tag, clothing, or jewelry items such as watches, rings,necklaces or bracelets. In one embodiment, the PDK 102 can be, forexample, about the size of a Subscriber Identity Module (SIM) card andbe as small as a square inch in area or less. In another embodiment, thePDK 102 can be easily contained in a pocket, on a keychain, or in awallet.

The memory 210 can be a read-only memory, a once-programmable memory, aread/write memory or any combination of memory types including physicalaccess secured and tamperproof memories. The memory 210 typically storesa unique PDK ID 212 and one or more profiles 220. The PDK ID 212comprises a public section and a private section of information, each ofwhich can be used for identification and authentication. In oneembodiment, the PDK ID 212 is stored in a read-only format that cannotbe changed subsequent to manufacture. The PDK ID 212 is used as anidentifying feature of a PDK 102 and distinguishes between PDKs 102 inprivate 116 or Central 114 registry entries. In an alternativeembodiment, the registries can identify a PDK 102 by a different ID thanthe PDK ID 212 stored in the PDK 102, or may use both the PDK ID 212 andthe different ID in conjunction. The PDK ID 212 can also be used inbasic PDK authentication to ensure that the PDK 102 is a valid device.

The profile fields 220 can be initially empty at the time of manufacturebut can be written to by authorized individuals (e.g., a Notary) and/orhardware (e.g., a Programmer). In one embodiment, each profile 220comprises a profile history 222 and profile data 230. Many differenttypes of profiles 220 are possible. A biometric profile, for example,includes profile data 230 representing physical and/or behavioralinformation that can uniquely identify the PDK owner. A PDK 102 canstore multiple biometric profiles, each comprising a different type ofbiometric information. In one embodiment, the biometric profile 220comprises biometric information transformed by a mathematical operation,algorithm, or hash that represents the complete biometric information(e.g., a complete fingerprint scan). In one embodiment, a mathematicalhash is a “one-way” operation such that there is no practical way tore-compute or recover the complete biometric information from thebiometric profile. This both reduces the amount of data to be stored andadds an additional layer of protection to the user's personal biometricinformation. In one embodiment, the biometric profile is further encodedusing a encoding key and/or algorithm that is stored with the biometricprofile data. Then, for authentication, both the biometric profile dataand the encoding key and/or algorithm are passed to the Reader 108.

In one embodiment the PDK 102 also stores one or more biometric profile“samples” associated with each biometric profile. The biometric profilesample is a subset of the complete profile that can be used for quickcomparisons of biometric data. In one embodiment, the profile samplescan be transmitted over a public communication channel or transmittedwith reduced level of encryption while the full biometric profiles areonly transmitted over secure channels. In the case of fingerprintauthentication, for example, the biometric profile sample may representonly small portion area of the full fingerprint image. In anotherembodiment, the fingerprint profile sample is data that describes an arcof one or more lines of the fingerprint. In yet another embodiment, thefingerprint profile sample can be data representing color information ofthe fingerprint.

In another embodiment, the stored profiles 220 include a PIN profilethat stores one or more PINs or passwords associated with the PDK owner.Here, the number or password stored in the PIN profile can be comparedagainst an input provided by the user at the point of transaction toauthenticate the user. In one embodiment, a PIN profile sample is alsostored with the PIN profile that comprises a subset of the full PIN. Forexample, a PIN profile sample can be only the first two numbers of thePIN that can be used to quickly compare the stored PIN profile to a PINobtained at the point of transaction.

In yet another embodiment, the PDK 102 stores a picture profile thatincludes one or more pictures of the PDK owner. In a picture profileauthentication, the picture stored in the PDK 102 is transmitted to adisplay at the point of transaction to allow an administrator (e.g., aclerk or security guard) to confirm or reject the identity of theindividual requesting the transaction. In another embodiment, an imageis captured of the individual at the point of transaction and comparedto the picture profile by an automated image analysis means.Furthermore, picture profiles could be used, for example, in place ofconventional passports or drivers licenses to authenticate the identityof an individual and allow for remote identification of individuals. Forexample, a police officer following a vehicle could obtain an image andidentity of the driver while still maintaining a safe distance from thevehicle. In the hospitality industry, a host could greet a guest at thedoor of a hotel, casino or restaurant and easily recognize the guest byobtaining the guest's picture profile as he/she enters.

A registry or database profile typically stores information associatingthe user with a registry. The registry profile can be used to determineif the individual is associated with the controlling entity for thatregistry and if different types of transactions are authorized for theindividual. A registry profile can further include additional userinformation for use with the registry. For example, a private registryprofile associated with a particular merchant may include a credit cardnumber that the user has selected as a default for that merchant. In oneembodiment, a profile can further include spending limits that limitsthe amount of purchases a user can make with a particular vendor orusing a particular profile.

A profile can further include personal identification information suchas name, address, phone number, etc., bank information, credit/debitcard information, or membership information. This information can beuseful for certain types of transactions. For example, with purchasesthat require delivery, a PDK 102 can automatically transmit addressinformation to the Reader 108 at the point of transaction. In oneembodiment, a profile can store multiple addresses. At the point oftransaction, the Reader 108 displays the address options and allows theuser to select which address to use.

Generally, some types of profile information (e.g., a biometric profile)can only be acquired during a trusted initialization process that isadministered by a trusted Notary. In one embodiment, other secureinformation such as credit card information are also stored to the PDKin the presence of a Notary. Alternatively, certain types of low-riskinformation can be added by the user without a Notary, such as, forexample a change of address. In another embodiment, once an initialprofile has been stored to the PDK 102, a user can add information tothe PDK 102 using a Programmer without a Notary throughself-authentication. For example, in one embodiment, a PDK 102 that hasa stored biometric profile can be “unlocked” by providing a matchingbiometric input. Then, once unlocked, the user can add or removeadditional profiles, credit cards, personal information, etc. to the PDK102 using a Programmer. For example, in one embodiment, a user that hasunlocked his/her own PDK 102 can store additional biometric information(such as fingerprint information for other fingers) in his/her PDK 102.In another example, a user that cancels a credit card, can unlockhis/her PDK 102 to remove the credit card information. In anotherembodiment, the user can make copies of the PDK 102 or move profilesfrom one PDK 102 to another once the PDK 102 is unlocked.

The profile history 222 includes a programmer ID field 224, a Notary ID226, and a site ID field 228. The profile history 222 relates to thespecific hardware, Notary, and site used at the time the profile datawas created and stored to the PDK. Typically each profile 220 stores itsspecific profile history 222 along with the profile data 230. Theprofile history 222 can be recalled for auditing purposes at a latertime to ensure the credibility of the stored data. In one embodiment,transaction history can also be stored to the PDK memory 210. Here, thePDK 102 stores information associated with any transactions made withthe PDK 102 such as the name of the merchant, the purchase amount,credit card used, etc.

The PDK 102 also includes a programmer I/O 240 that provides aninterface to a trusted Programmer (not shown). The Programmer comprisestrusted hardware that is used to program the memory 210 of the PDK 102.An example embodiment of a Programmer is described in more detail belowwith reference to FIG. 9. The programmer I/O 240 can be, for example, aUSB interface, serial interface, parallel interface, or any other director wireless link for transferring information between the PDK 102 andthe Programmer. When coupled to the Programmer, the programmer I/O 240receives initialization data, registration data or other information tobe stored in the memory 210.

The control logic 250 coordinates between functions of the PDK 102. Inone embodiment, the control logic 250 facilitates the flow ofinformation between the programmer I/O 240, transceiver 260 and memory210. The control logic 250 can further process data received from thememories 210, programmer I/O 240 and transceiver 260. Note that thecontrol logic 250 is merely a grouping of control functions in a centralarchitecture, and in other embodiments, the control functions can bedistributed between the different modules of the PDK 102. The operationof the control logic will be understood to those skilled in the artbased on the description below corresponding to FIGS. 4-7D.

The transceiver 260 is a wireless transmitter and receiver forwirelessly communicating with a Reader 108 or other wireless device. Thetransceiver 260 can send and receive data as modulated electromagneticsignals. Moreover, the data can be encrypted by the transceiver 260 andtransmitted over a secure link. Further, the transceiver 260 canactively send connection requests, or can passively detect connectionrequests from another wireless source. In one embodiment, thetransceiver 260 is used in place of a separate programmer I/O 240 and isused to wirelessly communicate with the Programmer for programming. Inone embodiment, the transceiver 260 is adapted to communicate over arange of up to around 5 meters.

Optionally, a PDK 102 can also include a built in biometric reader (notshown) to acquire a biometric input from the user. The biometric inputcan be used to unlock the PDK 102 for profile updates, or for varioustypes of authentication. For example, in one embodiment, a biometricinput is received by the PDK 102 and compared to stored biometricinformation. Then, if the user is authenticated, the PDK 102 canindicate to the Reader 108 that the user is authenticated and transmitadditional information (e.g., a credit card number) needed to complete atransaction.

Turning now to FIG. 3, an example embodiment of a Reader 108 isillustrated. The embodiment includes one or more biometric readers 302,a receiver-decoder circuit (RDC) 304, a processor 306, a networkinterface 308, an I/O port 312 and optionally a credit card terminal I/O310. In alternative embodiments, different or additional modules can beincluded in the Reader 108.

The RDC 304 provides the wireless interface to the PDK 102. Generally,the RDC 304 wirelessly receives data from the PDK 102 in an encryptedformat and decodes the encrypted data for processing by the processor306. An example embodiment of an RDC is described in U.S. patentapplication Ser. No. 11/292,330 entitled “Personal Digital Key AndReceiver/Decoder Circuit System And Method”, the entire contents ofwhich are incorporated herein by reference. Encrypting data transmittedbetween the PDK 102 and Reader 108 minimizes the possibility ofeavesdropping or other fraudulent activity. In one embodiment, the RDC304 is also configured to transmit and receive certain types ofinformation in an unencrypted, or public, format.

The biometric reader 302 receives and processes the biometric input 104from an individual at the point of transaction. In one embodiment, thebiometric reader 302 is a fingerprint scanner. Here, the biometricreader 302 includes an image capture device adapted to capture theunique pattern of ridges and valleys in a fingerprint also known asminutiae. Other embodiments of biometric readers 302 include retinalscanners, iris scanners, facial scanner, palm scanners, DNA/RNAanalyzers, signature analyzers, cameras, microphones, and voiceanalyzers. Furthermore, the Reader 108 can include multiple biometricreaders 302 of different types. In one embodiment, the biometric reader302 automatically computes mathematical representations or hashes of thescanned data that can be compared to the mathematically processedbiometric profile information stored in the PDK 102.

The processor 306 can be any general-purpose processor for implementinga number of processing tasks. Generally, the processor 306 processesdata received by the Reader 108 or data to be transmitted by the Reader108. For example, a biometric input 104 received by the biometric reader302 can be processed and compared to the biometric profile 220 receivedfrom the PDK 102 in order to determine if a transaction should beauthorized. In different embodiments, processing tasks can be performedwithin each individual module or can be distributed between localprocessors and a central processor. The processor 306 further includes aworking memory for use in various processes such as performing themethod of FIGS. 4-7D.

The network interface 308 is a wired or wireless communication linkbetween the Reader 108 and one or more external databases such as, forexample, a validation database 112, the Central Registry 114 or aprivate registry 116. For example, in one type of authentication,information is received from the PDK 102 at the RDC 304, processed bythe processor 306, and transmitted to an external database 112-116through the network interface 308. The network interface 308 can alsoreceive data sent through the network 110 for local processing by theReader 108. In one embodiment, the network interface 308 provides aconnection to a remote system administrator to configure the Reader 108according to various control settings.

The I/O port 312 provides a general input and output interface to theReader 108. The I/O port 312 may be coupled to any variety of inputdevices to receive inputs such as a numerical or alphabetic input from akeypad, control settings, menu selections, confirmations, and so on.Outputs can include, for example, status LEDs, an LCD, or other displaythat provides instructions, menus or control options to a user.

The credit card terminal I/O 310 optionally provides an interface to anexisting credit card terminal 314. In embodiments including the creditcard terminal I/O 310, the Reader 108 supplements existing hardware andacts in conjunction with a conventional credit card terminal 314. In analternative embodiment, the functions of an external credit cardterminal 314 are instead built into the Reader 108. Here, a Reader 108can completely replace an existing credit card terminal 314.

In one embodiment, a Reader 108 is adapted to detect and preventfraudulent use of PDKs that are lost, stolen, revoked, expired orotherwise invalid. For example, the Reader 108 can download lists ofinvalid PDKs IDs 212 from a remote database and block these PDKs 102from use with the Reader 108. Furthermore, in one embodiment, the Reader108 can update the blocked list and/or send updates to remote registries114-116 or remote Readers 108 upon detecting a fraudulently used PDK102. For example, if a biometric input 104 is received by the Reader 108that does not match the biometric profile received from the PDK 102, theReader 108 can obtain the PDK ID 212 and add it to a list of blocked PDKIDs 212. In another embodiment, upon detecting fraudulent use, theReader 108 can send a signal to the PDK 102 that instructs the PDK 102to deactivate itself. The deactivation period can be, for example, afixed period of time, or until the rightful owner requests re-activationof the PDK 102. In yet another embodiment, the Reader 108 can send asignal instructing the fraudulently obtained PDK 102 to send alarmsignals indicating that the PDK 102 a stolen device. Here, a stolen PDK102 can be tracked, located and recovered by monitoring the alarmsignals. In one embodiment, the Reader 108 stores biometric or otheridentifying information from an individual that attempts to fraudulentlyuse a PDK 102 so that the individual's identity can be determined.

Generally, the Reader 108 is configured to implement at least one typeof authentication prior to enabling a transaction. In many cases,multiple layers of authentication are used. A first layer ofauthentication, referred to herein as “device authentication”, beginsany time a PDK 102 moves within range of a Reader 108. In deviceauthentication, the Reader 108 and the PDK 102 each ensure that theother is valid based on the device characteristics, independent of anyprofiles stored in the PDK 102. In some configurations, when fast andsimple authentication is desirable, only device authentication isrequired to initiate the transaction. For example, a Reader 108 may beconfigured to use only device authentication for low cost purchasesunder a predefined amount (e.g., $25). The configuration is also usefulin other types of low risk transactions where speed is preferred overadditional layers of authentication.

Other configurations of the Reader 108 require one or more additionallayers of authentication, referred to herein as “profile authentication”based on one or more profiles stored in the PDK 102. Profileauthentication can include, for example, a biometric authentication, aPIN authentication, a photo authentication, a registry authentication,etc. or any combination of the above authentication types. Profileauthentications are useful when a more exhaustive authentication processis desired, for example, for high purchase transactions or for enablingaccess to classified assets.

FIG. 4 illustrates an example embodiment of a process for secureauthentication of a transaction. When a PDK 102 comes within range of aReader 108, communication is automatically established 402 between theRDC 304 of the Reader 108 and the PDK 102. In one embodiment, the RDC304 continually transmits beacons that are detected by the PDK 102 whenit enters a proximity zone of the Reader 108. In an alternativeembodiment, the communication is instead initiated by the PDK 102 andacknowledged by the Reader 108. Generally, initial communication betweenthe Reader 108 and the PDK 102 is not encrypted in order to providefaster and more power efficient communication.

In step 404, a device authentication is performed. Here, the Reader 108establishes if the PDK 102 is a valid device and PDK 102 establishes ifthe Reader 108 is valid. Furthermore, device authentication determinesif the PDK is capable of providing the type of authentication requiredby the Reader 108.

An example embodiment of a method for performing 404 deviceauthentication is illustrated in FIG. 5. The RDC 304 receives andanalyzes 502 information from the PDK 102; and the PDK 102 receives andanalyzes 502 information received from the RDC 304. Generally, thisinitial information is transmitted over a public communication channelin an unencrypted format. Based on the received information, each device102, 304 determines 504 if the other is valid. As will be apparent toone of ordinary skill in the art, a number of different protocols can beused for this type of authentication such as, for example, achallenge-response authentication or a challenge handshakeauthentication protocol (CHAP). If either of the devices 102, 304 isinvalid 512, the process ends. If both the PDK 102 and the RDC 304 aredetermined by the other to be valid, the Reader 108 requests andreceives 506 authentication type information from the PDK 102 indicatingthe different types of authentication the PDK 102 is capable ofsatisfying based on the types of profiles the PDK 102 stores. Theavailable profile types in the PDK 102 are compared against theauthentication types that can be used by the Reader 108. For example, aparticular Reader 108 may be configured to perform only a fingerprintauthentication and therefore any PDK without a fingerprint biometricprofile cannot be used with the Reader 108. In one embodiment, theReader 108 can allow more than one type of profile to be used. Inanother embodiment, the Reader 108 requires more than one type ofprofile for authentication, while in yet further embodiments no profileauthentications are required. Next, the method determines 508 whetherthe PDK 102 has one or more profiles sufficient for authentication. Ifthe PDK 102 does not have one or more profiles sufficient forauthentication with the Reader 108, the devices 102, 304 are determinedto be invalid 512 because they cannot be used with each other. If thePDK 102 does have one or more sufficient types of profiles, the devicesare valid 510.

Turning back to FIG. 4, if either the PDK 102 or RDC 304 is not foundvalid during device authentication 404, the transaction is notauthorized 418 and the process ends. If the devices are valid, the RDC304 temporarily buffers 408 the received PDK information. It is notedthat in one embodiment, steps 402-408 are automatically initiated eachtime a PDK 102 enters the proximity zone of the Reader 108. Thus, ifmultiple PDKs 102 enter the proximity zone, the Reader 108 automaticallydetermines which PDKs 102 are valid and buffers the received informationfrom each valid PDK 102.

The method next determines 410 whether profile authentication isrequired based on the configuration of the Reader 108, the type oftransaction desired or by request of a merchant or other administrator.If the Reader 108 configuration does not require a profileauthentication in addition to the PDK authentication, then the Reader108 proceeds to complete the transaction for the PDK 102. If the Reader108 does require profile authentication, the profile authentication isperformed 412 as will be described below with references to FIGS. 6-7D.If a required profile is determined 414 to be valid, the Reader 108completes 416 the transaction. Otherwise, the Reader 108 indicates thatthe transaction is not authorized 418. In one embodiment, completing 416the transaction includes enabling access to secure physical or digitalassets (e.g., unlocking a door, opening a vault, providing access to asecured hard drive, etc.). In another embodiment, completing 416 thetransaction includes charging a credit card for a purchase.Alternatively, bank information, debit/check/ATM card information,coupon codes, or any other purchasing means information (typicallystored in a profile memory field 232) can be transmitted by the PDK 102in place of credit card information. In one embodiment, the PDK 102 isconfigured with multiple purchasing means and a default is configuredfor different types of transactions. In another embodiment, each creditcard or other purchasing means is displayed to the customer by theReader 108 and the customer is allowed to select which to use for thetransaction.

Turning now to FIG. 6, an embodiment of a process for profileauthentication is illustrated. In step 602, a secure communicationchannel is established between the RDC 304 and the PDK 102. Informationsent and received over the secure channel is in an encrypted format thatcannot be practically decoded, retransmitted, reused, or replayed toachieve valid responses by an eavesdropping device. The Reader 108transmits 604 profile authentication requests to the PDK 102 requestingtransmission of one or more stored profiles over the secure channel. At608, the process determines whether a “trigger” is required forauthentication. The requirement for a trigger depends on theconfiguration of the Reader 108, the specific type of transaction to beexecuted and the type of authentication requested.

In a first configuration, a trigger is required to continue the processbecause of the type of authentication being used. For example, inbiometric authentication, the authentication process cannot continueuntil the Reader detects a biometric contact and receives biometricinformation. It is noted that biometric contact is not limited tophysical contact and can be, for example, the touch of a finger to afingerprint scanner, the positioning of a face in front of a facial orretinal scanner, the receipt of a signature, the detection of a voice,the receipt of a DNA sample, RNA sample, or derivatives or any otheraction that permits the Reader 108 to begin acquiring the biometricinput 104. By supplying the biometric contact, the user indicates thatthe authentication and transaction process should proceed. For example,a PDK holder that wants to make a withdrawal from an Automated TellerMachine (ATM) equipped with a Reader 108 initiates the withdrawal bytouching a finger to the Reader 108. The ATM then begins the transactionprocess for the withdrawal.

In a second configuration, some other user action is required as atrigger to proceed with the transaction even if the authenticationprocess itself doesn't necessarily require any input. This can be usedfor many purchasing transactions to ensure that the purchase is notexecuted until intent to purchase is clear. For example, a Reader 108 ata gas station can be configured to trigger the transaction when acustomer begins dispensing gas. At a supermarket, a Reader 108 can beconfigured to trigger the transaction when items are scanned at acheckout counter.

In a third configuration, no trigger is used and the Reader 108automatically completes the remaining authentication/transaction with noexplicit action by the user. This configuration is appropriate insituations where the mere presence of a PDK 102 within range of theReader 108 is by itself a clear indication of the PDK owner's desire tocomplete a transaction. For example, a Reader 108 can be positionedinside the entrance to a venue hosting an event (e.g., a sporting event,a concert, or a movie). When a PDK owner walks through the entrance, theReader 108 detects the PDK 102 within range, authenticates the user, andexecutes a transaction to purchase an electronic ticket for the event.In another embodiment, the electronic ticket can be purchased inadvance, and the Reader 108 can confirm that the user is a ticket holderupon entering the venue. Other examples scenarios where thisconfiguration is useful include boarding a transportation vehicle (e.g.,a train, bus, airplane or boat), entering a hotel room, or accessingsecure facilities or other assets. Thus, if no trigger is required, theprocess next performs 614 the requested profile authentication tests.

If a trigger is required, the Reader monitors 610 its inputs (e.g., abiometric reader, key pad, etc.) and checks for the detection 612 of atrigger. If the required trigger is detected, the process continues toperform 614 one or more profile authentication test. FIGS. 7A-7Dillustrate various embodiments of profile authentication tests.According to different configurations of the Reader 108, one or more ofthe illustrated authentication processes may be used. Further, in someembodiments, one or more of the processes may be repeated (e.g., fordifferent types of biometric inputs).

Referring first to FIG. 7A, it illustrates a process for biometricauthentication. In biometric authentication, a Reader 108 compares abiometric profile stored in the PDK 102 to the biometric input 104acquired by the biometric reader 302. Advantageously, the biometricinput 104 is not persistently stored by the Reader 108, reducing therisk of theft or fraudulent use. If 702 biometric authentication isrequested, the Reader 108 scans 704 the biometric input 104 supplied bythe user. In one embodiment, scanning 704 includes computing amathematical representation or hash of the biometric input 104 that canbe directly compared to the biometric profile.

Furthermore, in one embodiment, scanning 704 also includes obtaining abiometric input sample from the biometric input according to the samefunction used to compute the biometric profile sample stored in the PDK102. Optionally, the Reader 108 receives 708 a biometric profile samplefrom the PDK 102 and determines 710 if the biometric profile samplematches the biometric input sample. If the biometric profile sample doesnot match the input sample computed from the scan, the profile isdetermined to be invalid 718. If the biometric profile sample matches,the full biometric profile 712 is received from the PDK 102 to determine714 if the full biometric profile 712 matches the complete biometricinput 104. If the profile 712 matches the scan, the profile 712 isdetermined to be valid 720, otherwise the profile 712 is invalid 718. Itis noted that in one embodiment, steps 708 and 710 are skipped and onlya full comparison is performed. In one embodiment, the biometric profileand/or biometric profile sample is encoded and transmitted to the Reader108 along with an encoding key and/or algorithm. Then, the Reader 108uses the encoding key and/or algorithm to recover the biometric profileand/or biometric profile sample. In another alternative embodiment, onlythe encoding key and/or algorithm is transmitted by the PDK 102 and thebiometric profile data is recovered from a remote database in an encodedform that can then be decoded using the key and/or algorithm.

It will be apparent to one of ordinary skill that in alternativeembodiments, some of the steps in the biometric profile authenticationprocess can be performed by the PDK 102 instead of the Reader 108 or byan external system coupled to the Reader 108. For example, in oneembodiment, the biometric input 104 can be scanned 704 using a biometricreader built into the PDK 102. Furthermore, in one embodiment, the stepsof computing the mathematical representation or hash of the biometricinput and/or the steps of comparing the biometric input to the biometricprofile can be performed by the PDK 102, by the Reader 108, by anexternal system coupled to the Reader 108, or by any combination of thedevices. In one embodiment, at least some of the information istransmitted back and forth between the PDK 102 and the Reader 108throughout the authentication process. For example, the biometric input104 can be acquired by the PDK 102, and transmitted to the Reader 108,altered by the Reader 108, and sent back to the PDK 102 for comparison.Other variations of information exchange and processing are possiblewithout departing from the scope of the invention. The transfer of databetween the PDK 102 and the Reader 108 and/or sharing of processing canprovide can further contribute to ensuring the legitimacy of eachdevice.

FIG. 7B illustrates a process for PIN authentication. If PINauthentication is requested 724, a PIN is acquired 726 from the userthrough a keypad, mouse, touch screen or other input mechanism.Optionally, the Reader 108 receives 728 a PIN sample from the PDK 102comprising a subset of data from the full PIN. For example, the PINsample can comprise the first and last digits of the PIN. If the Reader108 determines 730 that the PIN sample does not match the input, theprofile is immediately determined to be invalid 736. If the PIN samplematches, the full PIN profile is received 732 from the PDK and comparedto the input. If the Reader 108 determines 734 that the profile matchesthe input, the profile is determined to be valid and is otherwiseinvalid 736. It is noted that in one embodiment, steps 728 and 730 areskipped.

FIG. 7C illustrates a process for a picture authentication. If theReader 108 determines 724 that picture authentication is requested, apicture profile is received 744 from the PDK 102 by the Reader 108 anddisplayed 746 on a screen. An administrator (e.g., a clerk, securityguard, etc.) is prompted 748 to compare the displayed picture to theindividual and confirms or denies if the identities match. If theadministrator confirms that the identities match, the picture profile isdetermined to be valid 764 and is otherwise invalid 752. In analternative embodiment, the process is automated and the administratorinput is replaced with a process similar to that described above withreference to FIG. 7A. Here, an image of the user is captured and facerecognition is performed by comparing picture profile informationreceived from the PDK 102 to the captured image.

FIG. 7D illustrates a process for authentication with a private registry114 or the Central Registry 116. If the Reader 108 determines thatregistry authentication is requested, a secure communication channel isestablished 762 over the network 110 between the Reader 108 and one ormore registries (e.g., the Central Registry 114, any private registry116, or other validation database 112). If any additional information isneeded to process the registry authentication (e.g., a credit cardnumber), the Reader 108 requests and receives the additional informationfrom the PDK 102. Identification information is transmitted 764 from theReader 108 to the registry 114-116 through the network interface 308.The PDK status is received 766 from the registry to determine 768 if thestatus is valid 772 or invalid 770. In one embodiment, the informationis processed remotely at the registry 114-116 and the registry 114-116returns a validation decision to the Reader 108. In another embodiment,the Reader 108 queries the private 116 or Central registry 114 forinformation that is returned to the Reader 108. The information is thenanalyzed by the Reader 108 and the authorization decision is madelocally. In one embodiment, the process involves transmitting creditcard (or other purchasing information) to a validation database 112 toauthorize the purchase and receive the status of the card. Statusinformation may include, for example, confirmation that the card isactive and not reported lost or stolen and that sufficient funds arepresent to execute the purchase.

Turning now to FIG. 8, a system 800 is illustrated for initializing andregistering a PDK 802 through secure trusted initialization andregistration processes. The system 800 comprises a Programmer 810, auser PDK 802, a Notary PDK 806, a network 110 and a set of externaldatabases including a validation database 112, a Central Registry 114and one or more private registries 116. The Programmer 810 couples tothe user PDK 802, the Notary PDK 806, and a network 110 by either wiredor wireless links. The Programmer 810 is also capable of receiving abiometric input 104 from a user and a control input 808 from either theuser or the Notary. The network 110 is coupled to the validationdatabase 112, the Central Registry 114 and two private registries 116.In alternative embodiments, different or additional external registriesor databases may be coupled to the network. In another alternativeembodiment, the Programmer can operate as a standalone device withoutany connection to the network 110.

Generally, the system 800 is adapted to initialize and/or register auser PDK 802 through a secure trusted process. Initialization includesconfiguring a user PDK 802 for at least its most basic use and caninclude acquiring one or more biometric profiles (or other profile) fromthe user according to a trusted process. The registration processregisters a user PDK 802 with the Central Registry 114 and/or one ormore private registries 116. Additionally, registration can includeprogramming profile memory fields 232 in the user PDK 802 to store, forexample, credit card information, personal information or otherinformation used for authentication or transaction purposes.

As previously mentioned, in one embodiment, the initialization processis administered and witnessed by a trusted third-party referred to as aNotary. Conceptually, a Notary can be thought of as an enhanced publicnotary that can be trusted to verify that an individual's identificationhas been properly authenticated prior to the execution of a transaction.Instead of witnessing an individual sign a legally-binding document, theNotary witnesses the acquisition and storage of an authenticatedindividual's biometric profile. The Notary ensures that the individual'sidentification and biometric profile comply with, and have been acquiredand processed according to defined security protocols. In oneembodiment, various requirements may be imposed on the Notary to beeligible for administering initialization and the requirements may bedefinable for different types of initialization. For example, in oneembodiment a Notary has to pass an extensive background check, receivetraining, or provide signatures agreeing to fulfill the duties of atrusted Notary. Furthermore, regular audits may be performed on Notariesto ensure that they can be trusted and are not associated with anyfraudulent activity. It is noted that not all types of initializationand registration require a Notary.

The initialization and registration processes are enabled by using aProgrammer 810 to write initialization and registration information to auser PDK 802. In one embodiment, the Programmer 810 also communicateswith a Notary PDK 806 belonging to a Notary that verifies the processesand ensures that the initialization and registration information can betrusted. For registration, the Programmer 810 communicates to theCentral Registry 114, one or more validation databases 112 or one ormore private registries 116 through the network 110.

FIG. 9 illustrates an example embodiment of a Programmer 810. TheProgrammer 810 includes one or more biometric readers 902, an interface904 for one or more PDKs, a storage module 910, a processor 906, acontrol interface 912, and a network interface 908.

It is noted that some of the modules of the Programmer 810 operatesimilarly to modules of the Touch Reader 108 previously described. Forexample, the biometric reader 902, network interface 908 and processor906 can be similar in architecture to the biometric reader 302, networkinterface 308 and processor 306 of the Touch Reader 108. However, theoperation of these components is as described below with reference toFIGS. 10-14. The PDK interface 904 couples the Programmer 810 to theprogrammer I/O 240 of one or more PDKs. In one embodiment, the PDKinterface 904 simultaneously couples to a Notary PDK 806 and a user PDK802. In another embodiment, two or more Notary PDKs 806 can be coupledto the interface 904 in addition to the user PDK 802. In yet anotherembodiment, the interface 904 only couples to one PDK at a time butallows different PDKs to be swapped in and out. In an alternativeconfiguration, the Notary PDK 806 can couple to the PDK interface 904from a remote location. For example, a Notary PDK 806 can couple to theProgrammer through a network, allowing the Notary to perform theinitialization from a remote location. In another configuration, theNotary function is performed by trusted hardware or other automatedmeans that can be built into the Programmer, rather than by a human.

The control interface 912 receives control inputs 808 from a user orfrom a Notary and outputs status indicators. Control inputs 808 caninclude, for example, programming settings, menu selections,confirmations and so on. Outputs can include, for example, status LEDs,an LCD with or without a touchscreen interface, or other display thatprovides instructions, menus or programming options to the user and/orNotary.

The storage module 910 temporarily stores user information duringprogramming. In one embodiment, the storage module 910 includes volatileand non-volatile memory. Typically, biometric information or otherhighly personal information is erased from the storage module 910 uponcompletion of programming or removal of the Notary PDK 806 or user PDK802. In one embodiment, the storage module 910 includes long-termstorage for storing programming history information. Programming historycan include, for example, the PDK ID, Notary ID, site ID, and timestampsassociated with the programming of any PDK. The programming history canbe recalled at a later time for auditing purposes.

Turning now to FIG. 10, an embodiment of a high-level process forinitializing a PDK is illustrated. To establish trust and credibility ofdata stored on the PDK, the Programmer validates 1002 a user andvalidates 1004 an Notary. The process for validation is described inmore detail below with reference to FIG. 11. Validation ensures thatboth the user and Notary are who they claim to be, that the user iseligible for PDK initialization, and that the Notary is authorized toadminister the registration process. In the case of a biometricinitialization, the Programmer 810 acquires 1006 biometric informationfrom the user for storage in a biometric profile of the user PDK 802.This process is described in more detail below with reference to FIG.12. The Programmer 810 can further acquire multiple types of biometricprofiles, or other types of user profiles. The initialization history isthen written 1008 to the PDK 802 and optionally to the Programmer 810for future auditing. This process is described in more detail below withreference to FIG. 12.

The steps of FIG. 10 are described in more detail with reference toFIGS. 11-13. FIG. 11 corresponds to a process for validating 1002 a userPDK 802 and the process for validating 1004 a Notary PDK 806. The userPDK 802 and Notary PDK 806 validation can occur in either order, or canbe processed in parallel. To begin validation, the Programmer 810detects 1102 a PDK 802/806 at the PDK interface 904. The Programmer 810next checks 1104 standing or status of the PDK 802/806 with the CentralRegistry 114. In the case of a user PDK 802, the Programmer 810 confirmswith the Central Registry 114 that the PDK 802 has not, for example,expired, been reported as lost or stolen, had fraudulent activityassociated with the PDK 802, or had any complaints been filed againstthe user for lack of payments, etc. Further, the Programmer 810 canconfirm that the software internal to the user PDK 802 is valid and hasnot been tampered with. In many cases, the user PDK 802 has never beenpreviously initialized or registered and automatically qualifies forgood standing. The step of checking 1104 the PDK standings vary slightlyfor an Notary PDK 806. Here, the check 1104 ensures that the Notary is aregistered Notary, that no fraudulent activity has been associated withthe Notary or any PDK initialized or registered by the Notary, that thesoftware internal to the Notary PDK 806 is valid and has not beentampered with, and that the Notary can be trusted to administer theinitialization. The process determines 1106 if the PDK (user 802 orNotary 806) is in good standing. If the PDK (user 802 or Notary 806) isdetermined to be in good standing, the initialization is allowed tocontinue 1110. If the PDK (user 802 or Notary 806) is not in goodstanding the initialization process ends 1108.

In one embodiment, validation further includes the PDK 802/806validating that the Programmer 810 is a valid trusted device. Thisvalidation ensures that the Programmer 810 has not been tampered withfor fraudulent use. Various device authentication processes are possiblesuch as, for example, a challenge-response authentication. Further, theProgrammer 810 can be validated by a remote registry to ensure itssoftware is update, the device has not been tampered with or thehardware has not been reported as lost, stolen, expired or revoked. Ifany fraudulent activity is detected with the Programmer, the Programmercan be automatically disabled.

Initialization optionally includes acquiring 1006 biometric informationto be stored in the biometric profile of the user PDK 802 asillustrating in FIG. 12. To begin the process, the Programmer 802requests 1202 biometric input 804 from the user. The biometric input 804is then scanned 1204 by the biometric reader 902. For example, in afingerprint-based initialization, scanning 1204 includes requesting theuser to place each desired finger on the biometric reader 902 of theProgrammer 810 and capturing an image representing the uniquecharacteristics of the fingerprint. In other types of biometricinitialization, scanning 1204 can include capturing a different type ofimage (e.g., a palm, face, retina, iris, or signature), capturing audiofor a voice-based biometric profile, or capturing DNA, RNA or theirderivatives as used to establish identity. The Programmer 810 checks1206 the quality of each scan to ensure that the captured biometricinput 804 is valid. If 1208 the quality is not satisfactory (due to, forexample, improper positioning during the scan), the Programmer 810repeats the request 1202 for biometric input 804. If 1208 the quality ofthe scan meets the necessary standards, the biometric profile iscomputed from the scan results. As previously described, the biometricprofile is generally computed by performing mathematical hashes on theacquired data. In addition, in one embodiment, the biometric profile canbe encoded according to an encoding key and/or algorithm that is storedwith the biometric profile data. This process can be repeated for anynumber of biometric profile types.

Additional types of profiles can also be similarly stored to the userPDK 802. For example, a PIN profile can be added by prompting the userto enter a PIN or password. A photo profile can be added by capturing animage of the user, checking the quality of the image and recapturing theimage if necessary.

FIG. 13 illustrates an embodiment of a process for writing 1008initialization data. In step 1302, the Programmer 810 receivesinitialization approval from the Notary. By submitting the approval, theNotary indicates that he/she has witnessed the initialization processand that the user's identity has been authenticated. In one embodiment,the approval can be executed automatically if all previous steps arevalidated. The acquired profile information and/or registry informationis then written 1304 to the user PDK 802. Here, user data can includethe profile to be written to the once-programmable memory or otherinformation to be written to the read/write memory fields. History datais also written 1306 to the user PDK. History data includes informationdocumenting the initialization process such as the Notary ID, theProgrammer's ID, and the site ID (indicating the location of theinitialization), registration date and time, and so on. Initializationhistory data can also be stored 1308 in the storage module 910 of theProgrammer 810. This provides an audit trail of all programmingoperations performed by the Programmer 810. It should be noted that theuser's biometric information is typically erased from the Programmer 810and is therefore not at risk of theft or fraudulent use.

In one embodiment, initialization history information is also written tothe Notary PDK 806. Here, a Notary PDK 806 can store a record of everyinitialization performed by the Notary. This information can be used forauditing purposes in the future. For example, if a Notary's rights arerevoked, any initializations performed by that Notary can be recoveredfrom the Notary's PDK 806. Then, user PDKs 802 initialized by thatNotary may need to be disabled until re-initialized by the user.

FIG. 14 illustrates a method for registering a PDK with a Central 114 orprivate 116 registry. In step 1402, the PDK initialization data isvalidated by the Programmer 810 to confirm that the PDK 802 has beenproperly initialized as described in FIGS. 10-13. The user is validated1404 and the Notary administering the registration is validated 1406. Inone embodiment, the validation steps can be executed by steps similar tothe process of FIG. 11 used in initialization. If the user and Notaryare both validated, the registry entry is added 1408 to the registry ifthe user is new to the registry, or a registry entry is updated 1408 ifthe user has already previously been registered. In this step, userinformation is transmitted by the network interface 908 of theProgrammer 810 to the private 116 or Central Registry 114. A registryentry can include for example, the unique user PDK, purchasinginformation (such as credit/debit/ATM card information or bank accountinformation), and personal information (such as name, address, phonenumber, date of birth, etc.). The user PDK 802 is then updated 1410 bystoring the information to the memory of the PDK. Information associatedwith a registry update (user PDK ID, Notary ID, programmer ID, site ID,registry ID, timestamps, etc.) can also be written to the storage module910 of the Programmer 810 to enable future audits. In an alternativeembodiment, the Programmer 810 can operate as a portable standalonedevice that can register a user PDK 802 in an offline mode. Then, theProgrammer can be later coupled to a network to upload any newregistrations to a private registry 116, Central Registry 114, orvalidation database 112.

It is noted that although in many embodiments of the present invention,the Notary performs the initialization and registration process inperson, it is also possible for the Notary to operate from a remotelocation. For example, in one embodiment, a user can enter aninitialization booth with a camera and a Programmer 810. The user entersthe user PDK 802 into the Programmer 810 and begins the initializationsession. A Notary at a remote location can monitor the operation and ifnecessary provide instructions to the user. Alternatively, theinitialization and registration can be administered by a completelyautomated process that can be recalled and reviewed at a later time toensure the user followed the appropriate procedures. In anotherembodiment, a human Notary is not required, and the initializationand/or registration processes are performed entirely by trustedhardware.

The order in which the steps of the methods of the present invention areperformed is purely illustrative in nature. The steps can be performedin any order or in parallel, unless otherwise indicated by the presentdisclosure. The methods of the present invention may be performed inhardware, firmware, software, or any combination thereof operating on asingle computer or multiple computers of any type. Software embodyingthe present invention may comprise computer instructions in any form(e.g., source code, object code, interpreted code, etc.) stored in anycomputer-readable storage medium (e.g., a ROM, a RAM, a magnetic media,a compact disc, a DVD, etc.). Such software may also be in the form ofan electrical data signal embodied in a carrier wave propagating on aconductive medium or in the form of light pulses that propagate throughan optical fiber.

While particular embodiments of the present invention have been shownand described, it will be apparent to those skilled in the art thatchanges and modifications may be made without departing from thisinvention in its broader aspect and, therefore, the appended claims areto encompass within their scope all such changes and modifications, asfall within the true spirit of this invention.

In the above description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofthe invention. It will be apparent, however, to one skilled in the artthat the invention can be practiced without these specific details. Inother instances, structures and devices are shown in block diagram formin order to avoid obscuring the invention.

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the invention. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment.

Some portions of the detailed description are presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the discussion, it isappreciated that throughout the description, discussions utilizing termssuch as “processing” or “computing” or “calculating” or “determining” or“displaying” or the like, refer to the action and processes of acomputer system, or similar electronic computing device, thatmanipulates and transforms data represented as physical (electronic)quantities within the computer system's registers and memories intoother data similarly represented as physical quantities within thecomputer system memories or registers or other such information storage,transmission or display devices.

The present invention also relates to an apparatus for performing theoperations herein. This apparatus can be specially constructed for therequired purposes, or it can comprise a general-purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program can be stored in a computerreadable storage medium, such as, but is not limited to, any type ofdisk including floppy disks, optical disks, CD-ROMs, andmagnetic-optical disks, read-only memories (ROMs), random accessmemories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any typeof media suitable for storing electronic instructions, and each coupledto a computer system bus.

The algorithms and modules presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems can be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatuses to perform the method steps. The required structure for avariety of these systems will appear from the description below. Inaddition, the present invention is not described with reference to anyparticular programming language. It will be appreciated that a varietyof programming languages can be used to implement the teachings of theinvention as described herein. Furthermore, as will be apparent to oneof ordinary skill in the relevant art, the modules, features,attributes, methodologies, and other aspects of the invention can beimplemented as software, hardware, firmware or any combination of thethree. Of course, wherever a component of the present invention isimplemented as software, the component can be implemented as astandalone program, as part of a larger program, as a plurality ofseparate programs, as a statically or dynamically linked library, as akernel loadable module, as a device driver, and/or in every and anyother way known now or in the future to those of skill in the art ofcomputer programming. Additionally, the present invention is in no waylimited to implementation in any specific operating system orenvironment.

It will be understood by those skilled in the relevant art that theabove-described implementations are merely exemplary, and many changescan be made without departing from the true spirit and scope of thepresent invention. Therefore, it is intended by the appended claims tocover all such changes and modifications that come within the truespirit and scope of this invention.

What is claimed is:
 1. A method comprising: establishing, at a readerdevice, a communication channel with a personal digital key (PDK);determining, at the reader device, that the PDK has a first status, afinancial transaction prevented when the PDK has a second status and anauthentication associated with the financial transaction initiated whenthe PDK has the first status; determining the authentication associatedwith the financial transaction based on a predefined criterionassociated with the financial transaction and based on a comparison ofone or more types of authentication profiles permitted by the readerdevice to one or more types of authentication profiles satisfiable bythe PDK; initiating, at the reader device, the authentication associatedwith the financial transaction which was determined based on thecomparison of one or more types of authentication profilesauthentication types permitted by the reader device to one or more typesof authentication profiles satisfiable by the PDK; determining, at thereader device, that a trigger indicative of intent to complete thefinancial transaction is required to continue authentication; receiving,at the reader device, information indicating that the trigger indicativeof intent to complete the financial transaction has been executed; andreceiving, at the reader device, payment means information from the PDKsubsequent to execution of the trigger and successful authentication ofa user, the payment means associated with a source of payment.
 2. Themethod of claim 1, comprising: determining a status of the PDK based atleast in part on a registry including data describing the status of oneor more PDKs; and determining that the PDK is in good standing, whereinthe first status is in good standing.
 3. The method of claim 2, whereinthe PDK is in good standing when not reported as lost, stolen, expiredor revoked.
 4. The method of claim 1, wherein the second status includesat least one of being lost, stolen, expired and revoked.
 5. The methodof claim 1, wherein the trigger indicative of intent to complete thefinancial transaction includes acquisition of a biometric input and thetrigger indicative of intent to complete the financial transaction isexecuted when a user's biometric input is received via a biometricscanner, the biometric input compared to a biometric profile stored onthe PDK, the successful authentication including a match between thebiometric input and the biometric profile stored on the PDK.
 6. Themethod of claim 5, wherein the biometric input is based on one or morefeatures of the user's finger.
 7. The method of claim 1, wherein the PDKis integrated into a cell phone.
 8. The method of claim 1, wherein thePDK is integrated into a watch.
 9. The method of claim 1, wherein thepayment means information is associated with a default payment means.10. The method of claim 1, wherein the payment means information isassociated a payment means selected by the user from a plurality ofpotential payment means associated with the user.
 11. A systemcomprising: one or more processors; and a memory storing instructionsthat when executed by the one or more processors, causes the system to:establish a communication channel between a personal digital key (PDK)and a reader; determine that the PDK has a first status, a financialtransaction prevented when the PDK has a second status and anauthentication associated with the financial transaction initiated whenthe PDK has the first status; determine the authentication associatedwith the financial transaction based on a predefined criterionassociated with the financial transaction and based on a comparison ofone or more types of authentication profiles permitted by the reader toone or more types of authentication profiles satisfiable by the PDK;initiate the authentication associated with the financial transactionwhich was determined based on the comparison of one or more types ofauthentication profiles authentication types permitted by the reader toone or more types of authentication profiles satisfiable by the PDK;determine that a trigger indicative of intent to complete the financialtransaction is required to continue authentication; receivinginformation indicating that the trigger indicative of intent to completethe financial transaction has been executed; and receiving payment meansinformation from the PDK subsequent to the execution of the trigger andsuccessful authentication of a user, wherein the PDK includes thepayment means information, the payment means associated with a source ofpayment.
 12. The system of claim 11 comprising: a network interfaceadapted to receive data describing the status of the PDK from a remoteregistry.
 13. The system of claim 11 comprising: a biometric readeradapted to obtain a representation of a physical or behavioralcharacteristic of the user.
 14. The system of claim 13, wherein thebiometric reader comprises at least one of a fingerprint scanner, aretinal scanner, an iris scanner, a face scanner, a palm scanner, a DNAanalyzer, a signature analyzer and a voice analyzer.
 15. The system ofclaim 11, wherein the first status is in good standing and the PDK is ingood standing when not reported as lost, stolen, expired or revoked. 16.The system of claim 11, wherein the second status includes at least oneof being lost, stolen, expired and revoked.
 17. The system of claim 13,wherein the trigger indicative of intent to complete the financialtransaction includes acquisition of a biometric input using thebiometric reader, the biometric input compared to a biometric profilestored on the PDK, the successful authentication including a matchbetween the biometric input and the biometric profile stored on the PDK.18. The system of claim 11, wherein the PDK is integrated into a cellphone.
 19. The system of claim 11, wherein the PDK is integrated into awatch.
 20. The system of claim 11, wherein the payment means informationis associated a payment means selected by the user from a plurality ofpotential payment means associated with the user.